-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent indexing of event.received
field
#11602
Conversation
This pull request does not have a backport label. Could you fix it @endorama? 🙏
NOTE: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Could you also check whether we need this for aggregated metrics data streams?
- Remove https://github.com/elastic/apm-server/blob/8.9/internal/beater/processors.go#L89 and its usage so that we can confirm the ingest pipeline works.
- System test to ensure the field is removed if possible
@@ -9,3 +9,8 @@ processors: | |||
name: observer_ids | |||
- pipeline: | |||
name: ecs_version | |||
- remove: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even better, define a pipeline like the one in https://github.com/elastic/apm-server/blob/main/apmpackage/cmd/genpackage/pipelines.go#L155 so that it can be reused in multiple ingest pipelines.
The same functionality is not handled in ingest pipelines
Replace previous implementation with the shared pipeline
event.received
field
event.received
fieldevent.received
field
Checked and I don't think we need to.
Done in 8ac04bd, thanks for pointing that out!
I reviewed the system tests and this is already tested. When removing the
The same tests pass when adding the ingest pipeline. Also is my understanding that as #11138 has not been completed APM events don't have |
apmpackage/apm/changelog.yml
Outdated
@@ -12,6 +12,9 @@ | |||
- description: Remove unused `processor.event` field from logs data streams | |||
type: enhancement | |||
link: https://github.com/elastic/apm-server/pull/11494 | |||
- description: Remove `event.received` fields from logs, metrics and traces data streams | |||
type: bugfix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
type: bugfix | |
type: enhancement |
There's no bug in apmpackage (mapping and ingest pipeline) itself
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, followed up in cee297b
After internal discussion we prefer keeping the current approach instead of moving to an ingest pipeline. I'm closing this PR as is no longer relevant. |
Motivation/summary
We added support for
event.received
field in elastic/apm-data#85.This field is useful to compute delay between event reception and ingestion, but is not currently used by APM UI.
To prevent ingesting unnecessary data, this PR adds a
remove
processor to ingest pipelines to prevent indexingevent.received
.Data streams updated:
app_logs
app_metrics
error_logs
internal_metrics
rum_traces
traces
Note for reviewers: I'm not sure if this PR needs to be backported.
Checklist
apmpackage
have been made)How to test these changes
Related issues
Related to #11138